Systems and methods for enabling third party engagements and services in host properties

ABSTRACT

A method for providing a third party engagement in a host property application is provided. The method includes: receiving an indication of an authentication of a user from the host property application such that additional authentication information for a third party that provides a third party engagement specific to the user is not required; determining that the user device is at or near a location of the third party; receiving an indication of an active user session associated with the host property application while the user device is at or near the location of the third party; generating a third party engagement specific to the user and associated with the third party; and providing, via a graphical user interface presented by a display device, the third party engagement specific to the user during the same active user session.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/953,929, entitled “Systems and Methods for Enabling Third PartyEngagements and Services in Host Properties,” filed Apr. 16, 2018, whichclaims the benefit of and priority to U.S. Provisional PatentApplication No. 62/614,284 entitled “Systems and Methods for EnablingThird Party Engagements and Services in Host Properties,” filed Jan. 5,2018, both of which are incorporated herein by reference in theirentireties.

TECHNICAL FIELD

The present disclosure relates to intelligently and strategicallyintegrating third party communications into host party properties.

BACKGROUND

People engage with various merchants daily. Many merchants provideloyalty programs where repeat engagements with that merchant enable thecustomer to earn various rewards (e.g., points, etc.). However,enrollment in these loyalty programs is typically burdensome to thecustomer. For example, the customer must register by providing theirname, address, a username, a password, answers to one more securityquestions, and perhaps even more information. To then access theirloyalty account, the customer must provide various credentials, such astheir username and password, which may be bothersome if the customer hasmultiple loyalty accounts with multiple credentials. Accordingly, betterloyalty program engagements are desirable.

SUMMARY

One embodiment relates to a system for providing a third partyengagement in a host property. The system includes a user device. Theuser device is structured to: provide an indication of an active usersession associated with a host property, the host propertycommunicatively coupled to a host property provider computing system;receive a third party engagement based on a trigger activated during theactive user session, the trigger structured to generate the third partyengagement; provide, via a graphical user interface comprising the hostproperty, the third party engagement based on the trigger activated; andreceive an indication of activation of the third party engagement.

Another embodiment relates to a system for providing a third partyengagement in a host property. The system includes a provider computingsystem communicatively coupled to a user device, the provider computingsystem structured to: receive an indication of an active user session ina host property; determine a trigger is activated during the active usersession, the trigger structured to generate a third party engagement;and generate the third party engagement based on the trigger activated,wherein the third party engagement is provided from within the hostproperty.

Still another embodiment relates to a computer implemented method ofproviding a third party engagement in a host property. The methodincludes: receiving an indication of an active user session in a hostproperty; determining a trigger is activated during the active usersession, the trigger structured to facilitate generation of a thirdparty engagement; generating the third party engagement based on thetrigger activated; and providing the third party engagement from withinthe host property to a user of the host property.

These and other features, together with the organization and manner ofoperation thereof, will become apparent from the following detaileddescription when taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a block diagram of a computing system according to an exampleembodiment.

FIG. 2 is a block diagram of a user device according to an exampleembodiment.

FIG. 3 is a flow diagram of a method of providing a third partyengagement in a host property, according to an example embodiment.

DETAILED DESCRIPTION

Referring to the Figures generally, systems and methods of providing athird party engagement in a host property are described herein. As usedherein, the term “third party engagement” refers to a communication(e.g., notification, etc.) regarding a product or service offering thatis provided within the context of a host property (e.g., an applicationrunning on a mobile device) to enable an enrollment or obtainment ofthat product or service from within the host property such that the userdoes not need to go off-property (e.g., to a property, such as awebsite, associated with the third party) to receive, obtain, orotherwise get that product or service. For example, a host property maybe a mobile wallet application provided by a first entity, while thethird party engagement is an offer for a cleaning service that isprovided to the user by a second entity while the user is in or usingthe mobile wallet application. In this regard, the communication for aproduct or service may also include, but is not limited to, an offer fora stored value card (e.g., a gift card), an offer for a loyalty card(or, more generally, to join a loyalty program), and the like. Thesystem includes a user device (e.g., a mobile device, wearable, etc.)that provides a host property. The system further includes an engagementsystem associated with an engagement system client application that isincluded with the user device. The engagement system is structured toreceive an indication of an active user session in the host property(i.e., that the user is using or in the host property); determinewhether a trigger is activated during the active user session; andgenerate the third party engagement based on the trigger activated. Theengagement system is further structured to provide the third partyengagement to a user via the user device.

The embodiments and implementations of the systems and methods disclosedherein improve current computing systems by facilitating the provisionof a third party engagement in a host property. As described herein, theengagement system improves authentication of computing systems. Usingthe engagement system, the identity of a person may be verified toprevent fraudulent activity and to ensure that each person who interactswith a host property operates under the proper security roles andpermissions. These systems, methods, and computer implementationsimprove such computing systems by facilitating the provision of thirdparty engagement in a host property without requiring the entry ofaccount information during an engagement with the third party providerduring an active user session using the host property. Without suchrequirements, the clock time, processing time, programmatic instructionsrequired to authenticate a user account, and other requirements of thecentral processing unit, memory utilization, and other system resourcesare reduced. Accordingly, authentication computing and system securityare improved by providing the ability to identify and verify a user of ahost property based on an application associated with the providerinstitution computing system such that the provision of additionalidentification information or account information by the user is notrequired.

These systems, methods, and computer implementations improve suchcomputing systems by facilitating the provision of third partyengagements in host properties. Advantageously, these systems, methods,and computer implementations enable a user to stay within a hostproperty (e.g., a host application) while selectively enrolling in thirdparty product and/or service from the host property. As such, thesystems, methods, and computer implementations disclosed herein improvethe functioning of such systems and information management by providingfunctionalities that are novel and non-obvious improvements over currentsystems.

Referring now to FIG. 1 , a block diagram of a computing system 100 isshown according to an example embodiment. As described herein, thecomputing system 100 facilitates third party engagements with a hostproperty without a user having to leave or exit the host property (e.g.,an application running on a user device). As shown, the computing system100 includes one or more user devices 110 associated with a user 101,one or more third parties 150 that are associated with a third partycomputing system 152, and a host property provider 170 having orassociated with a host property provider computing system 172. Thecomponents of FIG. 1 may be communicably and operatively coupled to eachother over a network 114. The network 114 may be any type of type ofnetwork. For example, the network 114 may be a wireless networkinterface (e.g., 802.11X, ZigBee, Bluetooth, Internet, etc.), a wirednetwork interface (e.g., Ethernet), or any combination thereof. Thenetwork 114 is structured to permit the exchange of data, values,instructions, messages, and the like between and among the user device110, the third party computing system 152, and the host propertyprovider computing system 172.

The host property provider 170 refers to an entity that provides one ormore host properties. As used herein, “host properties” refer toapplications that run on a user device 110 (described below). Thus, the“host property” may be a mobile application when the user device 110 isa mobile device 120. When the user device 110 is a predominately fixeddevice (e.g., a desktop computer), the “host property” is a desktopapplication. In the example depicted, the host property provider 170 isa financial institution capable of providing one or more financialproducts and services (e.g., banking (e.g., the providing of variousaccounts, such as a demand deposit account), lending, money transfers,issuing credit and/or debit cards, wealth management, and so on). Thus,the associated host property provider computing system 172 is structuredto provide or otherwise facilitate providing the one or more financialproducts and services to customers. As such, the financial institutionmay provide banking services to the customers. For example, customerscan deposit funds into accounts, withdraw funds from accounts, transferfunds between accounts, view account balances, and the like via the hostproperty provider computing system 172. As described herein, thecomputing system 172 is structured to facilitate the provision of athird party engagement in a host property. In this regard, the hostproperty provider computing system 172 is a backend computer system thatsupports the user device 110 and other services offered by the provider,e.g., financial services offered by the provider institution.

As shown, the host property provider computing system 172 includes aprocessor 174 and a memory device 176. The processor 174 may beimplemented as a general-purpose processor, an application specificintegrated circuit (ASIC), one or more field programmable gate arrays(FPGAs), a digital signal processor (DSP), a group of processingcomponents (e.g., servers), or other suitable electronic processingcomponents. The one or more memory devices 176 (e.g., RAM, ROM, NVRAM,Flash Memory, hard disk storage, etc.) may store data and/or computercode for facilitating at least some of the various processes describedherein. In this regard, the memory 176 may store programming logic that,when executed by the processor 174, control the operation of the hostproperty provider computing system 172.

As shown, the host property provider computing system 172 also includesa network interface 178. The network interface 178 facilitates thesending and receiving of data, information, and/or communications overthe network 114 (e.g., to and from the user device 110, etc.). Asmentioned above, in this example, the host property provider 170 isstructured as a financial institution. As such, the host propertyprovider computing system 172 may also include an account database 180that stores customer information and account information relating toaccounts held with the financial institution. As further shown, thecomputing system 172 may include a mobile wallets account database 182for storing mobile wallet accounts of users. As described herein below,the mobile wallet accounts may permit payments via the mobile walletclient application 130.

The account database 180 is structured to maintain accounts associatedwith customers of the provider 170 and to facilitate transactionsassociated with the accounts. The account database 180 may storetransaction data and account information, including account numbers,account balances, customer contact information, customer preferences,and other account information. As used herein, the term “transactiondata” may be used to refer to data associated with a transactionincluding, but not limited to, a payment, expense, debit, credit,contribution, donation, etc. which may be associated with the account ofa user of the provider 170.

The mobile wallets database 182 is structured to store informationregarding mobile wallet accounts held by various users, such as for amobile wallet account held by the user of the user device 110. Forinstance, the mobile wallets database 182 may store various forms ofinformation related to the user and/or an associated mobile device uponregistration of one or both for a mobile wallet. The stored mobilewallet account information may include authentication information (e.g.,username/password combinations, device authentication tokens, securityquestion answers, etc.), payment card information, and transactionhistory, account holder identifying information, registered deviceinformation, and any other information that may be encountered in theoperation of a mobile wallet account or otherwise referenced herein.Such information may include user preferences and other informationcomprising a user profile. In some arrangements, for example, mobilewallets database 182 also includes or is coupled to a token vault. Thetoken vault may include a lookup table maintaining tokens associatedwith various user payment vehicles. The tokens stored therein may begenerated internally (e.g., at the host property provider computingsystem 172) or by other entities (e.g., a token service providercomputing system). For example, in one embodiment, the token vault mayinclude a lookup table including tokens that that have been randomlyassigned to a user payment vehicle (e.g., user lines of credit, userchecking accounts, and the like). In some arrangements, the computingsystem 172 may include an associated token management system (not shown)including one or more algorithms, processes, formulas, etc. thatfacilitate the efficient searching of the information stored in thetoken vault. For example, a mapping algorithm may be utilized to mapToken-to-PAN information. Thus, when a token is received, the mappingalgorithm determines the associated PAN and sends that information tothe issuer. In some arrangements, the token vault is provided at acomputing system associated with a separate entity.

The engagement system 138 refers to one or more server, processing,memory or storage, network, and the like components that may at leastpartly support the engagement system client application 140 that may bedownloaded and run on the user device 110. In the example shown, apartnership database 136 is included with the engagement system 138. Thedatabase 136 is structured to store information relating to thepartnerships established: for example, the products offered by one ormore third parties 150, conditions for use associated therewith, and anyother information relating to the third party(ies). In this regard, thedatabase 136 may store the pre-generated one or more products from themthe third parties 150, such that the engagement system clientapplication 140 can easily and readily offer and activate suchproduct(s). Therefore, in operation, the engagement system 138 may atleast partially support some of the activities described herein withrespect to the engagement system client application 140.

The computing system 100 also includes one or more third parties 150owning, operating, or otherwise associated with one or more third partycomputing systems 152. The third parties refer to one or more persons,groups of persons, or entities that are a third party relative to thehost property provider (i.e., in this example, the financialinstitution). The third parties 150 may offer one or more products orservices. In the example depicted, the third parties 150 refer tomerchants (e.g., Walgreens, etc.). The merchants may sell variousproducts (e.g., household goods, car parts, etc.). The merchants mayalso offer a loyalty or rewards program. The loyalty program providesbenefits to repeat customers. For example, the more a user spends whileshopping at a merchant, the more points that are earned by the userwhich can be converted into some form of useful currency (e.g., a giftcard, cash redemption, a gift, a voucher, etc.). The merchant mayprovide a loyalty card to a user, which is associated with the loyaltyaccount of the user at that merchant. The loyalty card can be swiped,dipped, and/or tapped at the merchant POS or the card number numericallyentered at the merchant's website, in order for the rewards to betracked to the customer's account associated with the loyalty card.

As shown, the third party computing system 152 includes a processor 154,a memory device 156, a network interface 158, an account database 160,and a product circuit 162. All of these components may be communicablyand operatively coupled to each other. The processor 154, memory device156, and network interface 158 may have the same structure and functionas described herein with respect to the processor 174, memory 176, andnetwork interface 178 of the host property provider computing system172.

The product circuit 162 is structured to provide one or more products tothe engagement system 140 to enable the third party engagement. Thus,the product circuit 162 may serve as a memory database or repository ofproducts that are offered by the third party (i.e., merchant). Forexample, the product circuit 162 may store electronic versions ofloyalty cards, electronic versions of stored value cards (e.g., giftcards), information regarding products or services offered by themerchant (e.g., car parts, etc.), and so on. The product circuit 162 mayprovide or otherwise facilitate provisioning of the one or more productsvia the network interface 158 over the network 114 to the engagementsystem 140.

The user 101 may have or be associated with a user device 110. The user101 may include individuals, business representatives, large and smallbusiness owners, and any other entity/person. In some configurations,the user 101 may have a financial account at the third parties 150 ofthe computing system 100. The user device 110 may be or include a mobiledevice 120 (i.e., a device that is substantially portable or movable asopposed to a stationary or fixed device). The mobile device 120 mayinclude a wearable device. Wearable devices refer to any type of devicethat a user wears including, but not limited to, a watch (e.g., a smartwatch), glasses (e.g., eye glasses, sun glasses, smart glasses, etc.),bracelet (e.g., a smart bracelet), etc. Mobile devices 120 may alsoinclude any type of mobile device of a user 101 including, but notlimited to, a phone (e.g., a smartphone, etc.) and a computing device(e.g., a tablet computer, a laptop computer, a person digital assistant,etc.). Mobile devices 120 may also include voice-activated digitalassistance devices (e.g., a voice activated device structured to assista user, smart speakers having chat bot capabilities, etc.), portablemedia devices, vehicle infotainment systems, etc. that may access one ormore programs, servers, networks, central computers, etc. Accordingly,the user device 110 may include a display device (e.g., a screen) andone or more input/output devices (e.g., a touch screen, microphone,speaker, keyboard, etc.). In the example depicted, the mobile device 120is structured as a smartphone.

In this example, the user device 110 includes an engagement systemclient application 140 coupled to a mobile wallet client application130. Thus, in this example, the mobile wallet or mobile walletapplication is the “host property.” Of course, in other arrangements, adifferent host property may be contemplated and utilized (e.g., a mobilebanking client application, a bill pay client application, apeer-to-peer payment application, a non-financially related clientapplication, and so on). The engagement system client application 140and mobile wallet client application 130 may be server-basedapplications executable on the user device 110. In this regard, a usermay have to first download the application(s) prior to their usage. Inanother embodiment, the engagement system client application 140 andmobile wallet client application 130 may be hard coded into the memoryof the user device 110. In an alternative embodiment, the engagementsystem client application 140 and mobile wallet client application 130may be web-based interface applications. In this configuration, the usermay have to log onto or access the web-based interface before usage ofthe application(s). The engagement system client application 140 andmobile wallet client application 130 may be at least partly supported bya separate computing system comprising one or more servers, processors,network interface modules, etc. that transmit the applications for useto the user device 110. In yet another alternative embodiment, themobile wallet client application 130 and the engagement system 140 mayinclude their own set of dedicated hardware components or substantiallydedicated hardware components and associated logic. To facilitateintegration, the engagement system client application 140 and mobilewallet client application 130 may include an application programminginterface (API) and/or a software development kit (SDK) that facilitatethe integration of other applications with at least one of theengagement system 140 and mobile wallet client application 130. All suchvariations and combinations are intended to fall within the spirit andscope of the present disclosure.

The mobile wallet client application 130 may be communicably coupled tothe host property provider computing system 172 (e.g., the mobilewallets database 182) via the network 114 and may be structured tofacilitate purchases by the user via the mobile wallet clientapplication 130. Accordingly, the mobile wallet client application 130may be linked or otherwise connected with one or more accounts of theuser. In this regard and as described above, the mobile wallet clientapplication 130 may be at least partly supported by the host propertyprovider computing system 172. In operation, when at a point-of-saleterminal, a user may open the mobile wallet client application 130 andprovide a passcode (e.g., biometrics such as a thumbprint, a personalidentification number (PIN), a password, etc.) to authenticate theperson and select the source payment account desired (e.g., a checkingaccount from a particular financial institution that is linked to themobile wallet client application 130). Via communication with thepayment terminal (e.g., via near field communication, Bluetooth, etc.),the aforementioned payment information may be provided and the paymentprocessed. Beneficially, carrying payment cards may be avoided orreduced via the mobile wallet client application 130.

The mobile wallet client application 130 is structured to permit mobilewallet users to engage in transactions through the initiation ofcommunications with, for example, a merchant point of sale device. Inthis regard, the mobile device 120 may include a near fieldcommunications (NFC) chip and an associated controller that configuresthe chip to exchange information with the merchant point of sale device(e.g., an NFC reader). It should be understood that the role that themobile wallet client application 130 takes in payment transactions willdepend on the implementation of the mobile wallet. In some arrangements,for example, the mobile wallet is implemented in a secure elementframework. In such arrangements, the mobile device 120 includes a secureelement that is separate from the main system memory of the user mobiledevice. The secure element may include any element having smart cardfunctionalities, such as a universal subscriber identity circuit (a SIMcard) or a secure digital card. In various other arrangements, theuser-specific payment information may be stored in a trusted executionenvironment (“TEE”) within a processor the user mobile device 120. Inthese arrangements, user authentication information (e.g., paymentvehicle information, user PINS, and the like) is stored in the secureelement. In various arrangements, the secure element of the mobiledevice 120 may include a payment application that interfaces with theNFC chip of the user device responsive to receiving a communication(e.g., an application protocol data unit) from the merchant point ofsale device to enable user payment information (e.g., a token) betransferred. In such arrangements, no user information is transferred bythe mobile wallet client application 130 to the NFC chip. After userpayment information is transmitted to the merchant point of sale device,the mobile wallet client application 130 may query the secure elementfor transaction data to notify the user of the completed transaction.

In other arrangements and in the example depicted, the mobile walletclient application 130 may operate under a host card emulationframework. In such arrangements, user payment information is maintainedwithin the mobile wallet client application 130 or cloud-basedenvironment (e.g., a host emulation service or the mobile walletsdatabase 182) rather than in the secure element. The user paymentinformation refers to the tokenized payment card information, which wasdescribed above. Thus, sensitive payment information is not stored bythe mobile device or application to improve security of thisinformation. In operation, the mobile wallet client application 130 mayinclude a service component (e.g., a payment application) configured tointerface with the NFC chip of the mobile device 120 to communicate userpayment tokens to the merchant point of sale device.

In some arrangements, the mobile wallet client application 130 isstructured to enable the user to manage a mobile wallet. In this regard,the mobile wallet client application 130 is structured to present,control, and otherwise manage displays or graphical user interfaces onthe mobile device 120 including information pertaining to variouspayment vehicles. For example, the mobile wallet client application 130may present the user with displays enabling the user to inputinformation pertaining to various payment vehicles. The screens mayenable the user to manually input information (e.g., a PAN) pertainingto a payment vehicle, or enable the user to take a picture of a paymentvehicle. The mobile wallet client application 130 may then process theinformation input by the user, identify account information, andtransmit the information to the computing system 172 for storage (e.g.,in the mobile wallets database 182 in association with the user). Onceinformation pertaining to various payment vehicles has been received bythe computing system 172, the mobile wallet client application 130 isconfigured to present displays that enable the user to select a paymentvehicle from amongst a plurality of payment vehicles. Once a paymentvehicle is selected, the displays may further enable the user to performvarious actions using the selected payment vehicle (e.g., use theselected vehicle to complete a mobile wallet transaction, manage anaccount at a financial institution associated with the selected paymentvehicle, view a transaction history associated with the payment vehicle,and the like).

As shown, the engagement system client application 140 is embodied withthe user device 110, and supported at least partly by the engagementsystem 138 of the host property provider computing system 172. In thisregard, the engagement system client application 140 may be structuredas a thin client application that is executable by a processor of theuser device 110. Accordingly, as will be appreciated by those ofordinary skill in the art, the description of the engagement systemclient application 140 in regard to the user device 110 is not meant tobe limiting as parts thereof may also be included with the computingsystem 172 (e.g., engagement system 138). With the above in mind and inthe example depicted, the mobile wallet client application 130 as wellas the engagement system 140 are configured as downloadable applicationsconfigured or structured to run on the user device 110.

Referring now to FIG. 2 , a block diagram of the user device 110 isshown according to an example embodiment. As mentioned above, in thisexample, the user device 110 is a mobile device 120 that is structuredas a smartphone. The user device 110 includes a processing circuit 201having a processor 202 and one or more memory devices 203. The processor202 may be implemented as a general-purpose processor, an applicationspecific integrated circuit (ASIC), one or more field programmable gatearrays (FPGAs), a digital signal processor (DSP), a group of processingcomponents that may be distributed over various geographic locations inthe user device, or other suitable electronic processing components. Theone or more memory devices 203 (e.g., RAM, NVRAM, ROM, Flash Memory,hard disk storage, etc.) may store data and/or computer code forfacilitating at least some of the various processes described herein.The one or more memory devices 203 may be or include tangible,non-transient/non-transitory computer readable medium, volatile memoryor non-volatile memory. Accordingly, the one or more memory devices 203may include database components, object code components, scriptcomponents, or any other type of information structure for supporting atleast some of the various activities and information structuresdescribed herein.

The user device 110 is shown to include various circuits and logic forcompleting at least some of the activities described herein. Moreparticularly, the user device 110 includes input/output logic 204, anetwork interface 205, a location circuit 206, the mobile wallet clientapplication 130, and the engagement system client application 140. Whilevarious circuits, interfaces, and logic with particular functionalityare shown in FIG. 2 , it should be understood that the user device 110may include any number of circuits, interfaces, and logic for completingthe functions described herein. For example, the activities of multiplecircuits may be combined as a single circuit, as additional circuitswith additional functionality may be included, etc.

The network interface 205 is adapted for and structured to establish acommunication session via the network 114 with at least one of the hostproperty provider computing system 172 and the third party computingsystem 152. Accordingly, the network interface 205 includes any of acellular transceiver (e.g., CDMA, GSM, LTE, etc.), a wireless networktransceiver (e.g., 802.11X, ZigBee, Bluetooth, etc.), or a combinationthereof (e.g., both a cellular transceiver and a Bluetooth transceiver).Further, the network interface 205 may include cryptography capabilitiesto establish a secure or relatively secure communication session withthe at least one host property provider computing system 172. In thisregard, data may be encrypted to prevent or substantially prevent thethreat of hacking.

The input/output logic 204 may be structured to receive and providecommunication(s) to a user of the device 110 (or, to another entity suchas the host property provider computing system 172). In this regard, theinput/output logic 204 may be structured to exchange data,communications, instructions, etc. with an input/output component of thedevice 110. Accordingly, in one embodiment, the input/output logic 204may include an input/output device such as a display device, atouchscreen, a keyboard, and a microphone. In another embodiment, theinput/output logic 204 may include communication circuitry forfacilitating the exchange of data, values, messages, and the likebetween an input/output device and the components of the user device 110(e.g., the engagement system client application 140). In yet anotherembodiment, the input/output logic 204 may include machine-readablemedia for facilitating the exchange of information between theinput/output device and the components of the user device 110. In stillanother embodiment, the input/output logic 204 may include anycombination of hardware components (e.g., a touchscreen, speakers,keyboards, notification LEDs, microphones, buttons, switches, cameras,and so on), communication circuitry, and machine-readable media.

The location circuit 206 may be structured to receive or acquirelocation data, and determine a location of the user device 110 based onthe location data. In one embodiment, the location circuit 206 mayinclude a global positioning system (GPS) or any other type of locationpositioning system. As such, the location circuit 206 may receivelatitude data, longitude data, and any other type of location orposition data to determine the location of the user device 110. In otherembodiments, the location circuit 206 may receive an explicit locationidentification from the user of the device 110. All such variations areintended to fall within the spirit and scope of the present disclosure.

As mentioned above, the mobile wallet client application 130 may bestructured to facilitate and permit payments by interfacing with anaccount (e.g., a checking account) held by the user at a financialinstitution. Accordingly, the mobile wallet client application 130 maybe communicably coupled via the network interface 205 over the network114 to the computing system 172.

While not shown, the user device 110 includes a power source. The powersource may include grid power, battery power (e.g., alkaline batteries,rechargeable batteries, etc.), and/or another energy source. As beingconfigured as a smartphone, the user device includes circuitrystructured to recharge the battery (i.e., the power source).

Turning now to the engagement system client application 140, asdescribed herein, the engagement system client application 140 isstructured to enable, provide, or otherwise facilitate third partyengagements with host properties. As shown, the engagement system clientapplication 140 includes a transaction circuit 142, a location circuit144, a matching circuit 146, and a communication circuit 148. Asmentioned above and in the example depicted, the engagement systemclient application 140 is structured as a downloadable applicationconfigured or structured to run on the user device 110. As such, thetransaction circuit 142, location circuit 144, matching circuit 146, andcommunication circuit 148 are embodied as machine or computer-readablemedia that is executable by a processor, such as the processor 202. Asdescribed herein and amongst other uses, the machine-readable mediafacilitates performance of certain operations to enable reception andtransmission of data. For example, the machine-readable media mayprovide an instruction (e.g., command, etc.) to, e.g., acquire data froma particular a physical sensor or a virtual sensor. In this regard, themachine-readable media may include programmable logic that defines thefrequency of acquisition of the data (or, transmission of the data). Thecomputer readable media may include non-transitory computer readablemedia, such as code, which may be written in any programming languageincluding, but not limited to, Java or the like and any conventionalprocedural programming languages, such as the “C” programming languageor similar programming languages. Of course, in other embodiments and asdescribed above, the circuits of the engagement system clientapplication may be hardware components or a combination of hardware andlogic components. For example, the circuits of the engagement system 140may take the form of one or more analog circuits, electronic circuits(e.g., integrated circuits (IC), discrete circuits, system on a chip(SOCs) circuits, microcontrollers, etc.), telecommunication circuits,hybrid circuits, and any other type of “circuit.” Both variations areintended to fall within the scope of the present disclosure.

The functionality of the user device 110 may be controlled at least inpart by the engagement system client application 140. The engagementsystem client application 140 is structured to manage theprovisioning/providing of a third party engagement in a host property toa user.

The transaction circuit 142 is structured to receive and/or acquiretransaction data regarding transactions of the user 101. Throughcoupling with the mobile wallet client application 130, the transactioncircuit 142 may receive transaction data regarding mobile walletpurchases/transactions. The transaction data regarding the mobile walletpurchases may include a determination of merchants frequented,transaction amounts, transaction dates, transaction locations, refundtransactions, and any other information relating to the mobile wallettransactions. As mentioned above, transaction data may also includenon-mobile wallet transactions as well, such as a payments, expenses,debits, credits, contributions, donations, etc. which may be associatedwith the account(s) of a user of the provider 170. As mentioned above,in this embodiment the host property provider 170 is a financialinstitution, such that the financial institution may have informationstored in its account database 180 regarding the non-mobile wallettransaction information. Thus, the transaction circuit 142 mayselectively ping, communicate, or otherwise request and receivetransaction data regarding mobile wallet and non-mobile wallettransactions. For example, the transaction circuit 142 may ping theaccount database 182 directly or indirectly via the engagement system138. Using the intermediary of the engagement system 138 may bebeneficial in providing an extra layer of security.

The location circuit 144 is structured to receive and/or acquirelocation data regarding the location of the user device 110. Forexample, the location circuit 144 may receive location data from thelocation circuit 206. As another example, the location data may beprovided from a separate device from the user device 110. For example,various user devices may be coupled to the engagement system 138, suchthat location data acquired from each of those devices may serve assource location data for the circuit 144 (e.g., location data from theuser's wearables and the mobile device). As such, one or more patternsmay be determined by the location circuit 144 regarding the activitiesof the user 101. The location circuit 144 may utilize artificialintelligence to determine predicted locations of the user 101 as well.This location data and predictive analytics may be used to ascertainpreferences of the user, such as where they like to frequent/visit andshop.

The matching circuit 146 is structured to match one or more productsoffered by one or more third parties 150 to the user 101 based on atleast one of the analyzed transaction data from the transaction circuit142, the location data from the location circuit 144, real-timetransactions, and/or a combination thereof. Thus, in operation, apartnership is established between the host property provider 170 andone or more third parties 150. Alternatively or additionally, anon-partnership is established between the host property provider 170and one or more third parties 150. In either situation, the matchingcircuit 146 is provided with at least partial access to third partycomputing system 152, and particularly, the product circuit 162. As aresult, the matching circuit 146 is provided access to the productsoffered by the one or more third parties 150, which are maintained andprovided by the product circuit 162. Alternatively, the product circuit162 may provide one or more products to the partnership database 136,such that the matching circuit 146 has access to the one or moreproducts in this manner rather than access the product circuit 162 thirdparty computing system 152 generally.

At least one of the third parties 150 or the host property provider 170may provide one or more terms and conditions for the one or moreproducts to define an offering condition. The offering conditiondictates when the one or more products may be offered to the user 101.For example, an offering condition may be that a predefined number oftransactions at a merchant must occur (e.g., three) before theirproduct, such as a loyalty card, is offered the user. As anotherexample, the host property provider 170 prioritizes various productsfrom various third parties (e.g., merchants) over others due to theterms of their agreement/partnership. For example, if third party A haspaid more to partner with the host property provider 170, their productsmay be prioritized over third party B.

In operation, the matching circuit 146 may firstly determine whichproducts are offered by which third parties. This information may bestored by the partnership database 136 of the engagement system 138. Inone embodiment, the matching circuit 146 queries the partnershipdatabase 136 to retrieve relevant partnership information (e.g.,identity of products and merchants or third parties, etc.). The receivedinformation may be stored by the engagement system 140 (e.g., in thememory 203 of the user device 110). In another embodiment, rather thanrequesting for information, partnership and product information may bepushed periodically from the partnership database 136 of the engagementsystem 138 to the matching circuit 146. The pushed information may bestored in a memory device of the user device (e.g., memory 203). Such aconfiguration may be beneficial to enable real-time or substantiallyreal-time matches of products to user. In either event, the matchingcircuit 146 establishes a knowledge of products offered by the thirdparties.

Notwithstanding the presence of absence of one or more offeringconditions, the matching circuit 146 is structured to identify and matchone or more products from one or more third parties based on at leastone of location data, transaction data, real-time transactions, and/or acombination thereof. For example, transaction data may indicate that theuser 101 frequents merchant X at least once a week. Accordingly, thematching circuit 146 may query the partnership database 136 of theengagement system 138 to determine if i) merchant X is in the system,and ii) merchant X offers a product. Or, as mentioned above, thematching circuit 146 may have this information such that theidentification can be done in real or substantially real time. Assumingthere is no prohibitive offering condition, the matching circuit 146 maydetermine that merchant X does offer a product that may be of interestto the user 101. As such, the matching circuit 146 determines thatbecause of the frequency which the user 101 shops at merchant X, theuser 101 may be interested in one or more products from merchant X.

The matching may also be performed based on location data. For example,the user 101 may frequent various merchant locations repeatedly (e.g.,weekly, as indicated by the location data for the past three weeks).While the user 101 does not shop at those locations such that thetransaction data alone may not provide an indication of a product match,the location data may be sufficient for the matching circuit 146 todetermine that the user 101 may be interested in one or more productsare offered by the merchants associated with the locations.Beneficially, this analysis may enable the user 101 to begin shopping atthose merchants. For example, the product may be a stored value cardthat would provide the user the ability to purchase a good that isnormally too pricey for them to consider. As a result, this product—thestored value card—may be used to initiate a relationship between theuser and that particular merchant. The matching may also be based onsome combination of location and transaction data.

While the matching circuit 146 is structured to identify various thirdparties (e.g., merchants) that may offer products of interest to theuser 101, the matching circuit 146 is also structured to identifyparticular products of interest to the user 101. For example, thetransaction data may indicate that a user visits a particular merchantat least once week. Due to this repeated engagement, the matchingcircuit 146 may determine that a loyalty card associated with thatmerchant that enables the user to earn rewards for shopping at thatparticular merchant may be the most appropriate product. As anotherexample, the location data may indicate that a user frequents aparticular merchant several times a month but seldom purchases a goodfrom that merchant based on the transaction data. Additionally, thematching circuit 146 may determine that the product offered by thatmerchant includes loyalty cards and stored value cards. Rather thansimply identifying a loyalty card as the product for the user, thematching circuit 146 determines that a stored value card may be moreappropriate because the stored value card may help the user shop morefrequently at that merchant.

Thus, the matching circuit 146 is structured to identify particularthird parties 150 and particular/specific products offered by thosethird parties that may be of interest/most appealing to the user 101. Itshould be understood that the matching circuit 146 may include one ormore matching algorithms, weighting processes, cross-referencing tables(e.g., look-up table(s)), and the like to enable this matching.

The communication circuit 148 is structured to communicate thedetermined matches to the user 101. More particularly, the communicationcircuit 148 is structured to communicate or provide the identifiedmatches (i.e., products) to the user 101 from within the host property.In the example depicted, the communication circuit 148 is structured tocommunicate the match—i.e., product—when the user is in the mobilewallet client application 130. The communication may be provided as apop-up in the client application 130. The communication may be providedas a push notification sent via the client application, which may showup on the user's lock screen of the mobile device 120. Thus, thecommunication circuit 148 may control certain components of the userdevice 110 (e.g., a speaker, a notification component such as a light, avibrating element, etc.) to selectively activate or utilize thesecomponents. Additionally or alternatively, the engagement system 140 mayprovide a user interface that integrates with the host property—i.e.,client application 130—that includes one or more icons that mayilluminate or otherwise notify the user of the products that may be ofinterest to them. All such variations are intended to fall within thescope of the present disclosure.

The communication circuit 148 is also structured to receive a responsebased on the communication. For example, the communication circuit 148may provide a notification of one or more matched products that isprovided via the client application 130. The user 101 may observe theproduct offer. The communication may also include one or more inputvehicles (a button, a link, etc.) provided on the graphical userinterface (GUI) of the host property. For example, the product may beshown on the GUI with a button that enables the user to click or tap itto achieve the product instantly or fairly instantly. The button mayinclude a “yes” or “no,” which allows the user to click yes or no. Ifyes is selected, in one embodiment, the product is instantly provided tothe user. In this embodiment, the engagement system client application140 may store one or more predefined products of interest for the userwhereby such products simply need to be activated to be used. In anotherembodiment, the communication circuit 148 sends a notification eitherdirectly or via the engagement system 138 to the third party computingsystem 152 to retrieve the product. In yet another embodiment, thepartnership database stores the product such that the retrieval messageis sent from the communication circuit 148 to the engagement system 138.In any event, the near real time fulfillment of these products isaccomplished. If no is selected, the communication circuit 148 mayprovide this information to the matching circuit 146 for the matchingcircuit 146 to curate future products for the user. Thus, the matchingcircuit 146 may utilize intelligence and machine learning to recognizeproducts that may be of interest and not interest for the user based ontheir responses to one or more provided products.

Beneficially, via the communication circuit 148 and engagement systemclient application 140, products are offered and able to be accepteddirectly in the host application (i.e., host property). Such a systemenables the user to save time without having to visit various merchantsor third parties, enables the merchant or third party to push theirproducts to consumers who may be interested in them, and otherwisecontinues to promote engagement with the host application.

Referring to FIG. 3 , a flow diagram of a method 300 of providing athird party engagement in a host property is described according to anexample embodiment. The third party engagement may include a third partyoffer, product, service, stored value card, loyalty card, etc. In somearrangements, the third party engagement may be generated and/orprovided in real-time or near real-time. In other arrangements, thecomputing system 100 may be configured to access a plurality of accountsof a customer that are spread across multiple provider institutions thatmay or may not be affiliated with the provider 170. Method 300 may beperformed by the components of FIGS. 1-2 , such that reference may bemade to them in explaining the method.

Prior to the provisioning of a third party engagement in a hostproperty, a user may be authenticated into the host property (i.e.,client application 130) at 301. In some examples, prior to allowing theuser to engage with the host property, the user may be authenticated asan account holder. The user may be authenticated based on authenticationcredentials of that user. The user can be identified and authenticatedbased on the application associated with the host property providercomputing system 172 such that the provisioning of additionalidentification information or account information by the user is notrequired. The user authentication data may include any of a password, aPIN (personal identification number), a user ID, an answer to averification question, a biometric, an identification of a securityimage, or a combination thereof. The client application 130 compares thereceived authentication data with known and verified user authenticationdata. If the authentication data provided does not match the known andverified user authentication data, the user is not authenticated. If theauthentication data provided matches the known and verified userauthentication data, the user is authenticated such that the user mayfreely or substantially freely (there may be additional securityprotocols provided that control the use of certain functions within thehost property) use the host property.

At 302, the engagement system client application 140 (e.g., via thecommunication circuit 148) receives an indication of an active usersession in a host property (e.g., a digital wallet and/or applicationassociated with a computing system 172 such as, but not limited to, aprovider computer system associated with a financial institution). Forexample, a user initiates, activates, or otherwise enters a user sessionin their digital/mobile wallet. In examples in which the user device 110includes a host property (e.g., an application) associated with the hostproperty provider computing system 172, the user authentication data(e.g., data indicative of the identity of a user of the providerinstitution and/or a user of various systems, applications, and/orproducts of the provider institution) received and/or transmitted to thecomputing system 172 may provide an indication of an active user sessionin the host property (e.g., a digital wallet). For example, the userauthentication data may indicate that the user is logged into the hostproperty. The host property may be associated with or otherwisecommunicatively coupled to one or more third party computing systems 152(e.g., one or more third party providers). In some examples, theengagement system client application 140 may be structured to monitoruser activity, user account information, user financial information,spending patterns, etc. such that the user activity may indicate thatthe user is engaged in an active user session.

In some examples, the engagement system client application 140 isfurther structured to determine whether a trigger is activated duringthe active user session at 304. The “trigger” refers to an indication ofwhen and if an offering of third-party products and/or services shouldbe made from within the host property. In other words, a “trigger”refers to a prompt for providing one or more third-party products.

The trigger may comprise an indication of an active enrollment/use ofthe host property (e.g., an enrollment at, during, and/or after thepoint of sale). For example, while the user is engaged in a transactioneither in a physical store or online (e.g., the user is checking out),the engagement system client application 140 may determine that the useris not enrolled in the loyalty program provided by the third partyprovider (e.g., a merchant). The engagement system client application140 may cross-reference the user account information associated with thecomputing system 172 against the known users associated with the thirdparty provider to determine whether the user is enrolled in or otherwiseassociated with a product, service, and/or offer provided by the thirdparty provider. In response to the determination that the user is notassociated with a product, service, and/or offer provided by the thirdparty provider (e.g., the user is not enrolled in the loyalty program),the engagement system client application 140 may generate a third partyengagement to provide the user the option to associate with a product,service, and/or offer provided by the third party provider (e.g., theoption to enroll in a loyalty program associated with the third partyprovider) based on the trigger comprising the active enrollment.

In some examples, the trigger may comprise a passive enrollment (e.g.,an enrollment based on transactions associated with a user account). Thematching circuit 146 may be structured to analyze transactions (e.g.,transaction history, trends, etc.) such that the trigger is based on oneor more transactions of a user. For example, the engagement systemclient application 140 may analyze the transactions associated with auser account to determine where the user shops and, in turn, provide athird party engagement to the user (e.g., the engagement system 140 mayprovide an offer to the user device 110 that asks the user to join aloyalty program provided by a merchant the user shops at). Then, atvarious predetermined times, the third party offer may be provided tothe user within the host application. This is a passive enrollmentbecause the offer is based on analyzed data and provided without a trueactivator as compared to the recognition of being at a POS device of amerchant and then offering a product to the user while he/she is at thePOS device (i.e., active enrollment).

Alternatively or additionally, as described above, the trigger maycomprise a location based on the location of a user device 106comprising the host property (e.g., the digital wallet). For example,while the user is engaged in a transaction at the point of sale (e.g.,the user is checking out), the engagement system 140 may determine thelocation of the user. The engagement system client application 140 mayutilize geolocation to determine that the user is located at a thirdparty provider and, in turn, provide the user the option to associatewith a product, service, and/or offer provided by the third partyprovider. For example, the engagement system client application 140 mayutilize geolocation to facilitate enrollment of the user in a loyaltyprogram (e.g., to ask the user if they want to provision a stored valuecard) provided by the third party provider. The engagement system clientapplication 140 may determine that the user is at or near a third partyprovider. While the user is at or near a particular location (e.g., athird party provider location), the engagement system client application140 may generate a third party engagement (e.g., a third party offer,stored value card, loyalty card, etc.) based on the trigger comprising alocation.

The engagement system client application 140 may be structured toprovide an indication of the activation of a trigger (e.g., an active,passive, and/or location based trigger) to facilitate and/or enable theshowing of a third party engagement (e.g., a product, offer, or service,etc.) to the user from within the host application.

The engagement system 140 may be structured to generate a third partyengagement based on the trigger activated at 306. As mentioned above,the third party engagement may be provided via the graphical userinterface comprising the host property (e.g., a digital wallet). Thethird party engagement may be generated in real-time or near real-timesuch that the user device 110 may be structured to receive the thirdparty engagement based on a trigger activated during the active usersession.

As mentioned above, the engagement system 140 may receive, via graphicaluser interface comprising the host property, an indication of activationof the third party engagement. For example, the user may provide anindication of activation by clicking a link, button, icon, image, etc.via the user device 110. In one embodiment, the product may be utilizedimmediately. This is due to the product being provided by the productcircuit 162 to the engagement system 138 for use. In another embodiment,a communication may need to be sent to the third party computing system152 to inform them of the acceptance before it is ready for use. Ineither situation, a communication may be provided from the communicationcircuit of the engagement system 140 to the third party computing system152 for them to update their records in the account database 160 of anenrollment with the product such that the friction that may be presentfor a user to start using the product is reduced/diminished. Theengagement system 138 directly or the engagement system 140 may transmitdata associated with the user to the third party 150 to enroll the userin or otherwise associate the user with the third party engagement(e.g., a third party product or service). In some examples, theengagement system 138 or engagement system client application 140 may bestructured to auto-fill the enrollment data via the user device 110comprising the graphical user interface. The user device 110 and/or theengagement system 138 may receive the enrollment data via an applicationprogram interface (API), which may be transmitted to the one or morethird parties. For example, a digital form, field, etc. included in thegraphical user interface may include user data, user accountinformation, etc. that is pre-filled such that the user is not requiredto input or provide data to complete acceptance of a third partyengagement. This may save time and be appealing to the user.

In response to receiving the indication of activation of the third partyengagement, the third party computing system 152 may generate a product,such as the digital stored value card. Alternatively and as describedabove, the product—the stored value card—may be pre-generated andautomatically given to the customer. The digital stored value card maybe associated with a third party user account (e.g., a third partyloyalty program account). In some examples, the digital stored valuecard may be displayed via a graphical user interface associated with thehost property. Alternatively or additionally, various features (e.g.,balance information, rewards, etc.) associated with the digital storedvalue card may be displayed via a graphical user interface associatedwith the host property. The engagement system 140 may transmit data toand/or receive data from one or more application program interfaces(APIs) associated with various third party systems. For example, theengagement system 140 may transmit a call, via an API, to receive and/ordisplay rewards information in real-time or near real-time in the hostproperty of the user device 110.

The embodiments described herein have been described with reference todrawings. The drawings illustrate certain details of specificembodiments that implement the systems, methods and programs describedherein. However, describing the embodiments with drawings should not beconstrued as imposing on the disclosure any limitations that may bepresent in the drawings.

It should be understood that no claim element herein is to be construedunder the provisions of 35 U.S.C. § 112(f), unless the element isexpressly recited using the phrase “means for.”

As used herein, the term “circuit” may be or include hardware structuredto execute the functions described herein. Alternatively and asdescribed above according to certain configurations, each respective“circuit” may be machine-readable media (e.g., code, programmable code,etc.).

In the hardware configuration, the circuit may be embodied as one ormore circuitry components including, but not limited to, processingcircuitry, network interfaces, peripheral devices, input devices, outputdevices, sensors, etc. In some embodiments, a circuit may take the formof one or more analog circuits, electronic circuits (e.g., integratedcircuits (IC), discrete circuits, system on a chip (SOCs) circuits,etc.), telecommunication circuits, hybrid circuits, and any other typeof “circuit.” For example, a circuit as described herein may include oneor more transistors, logic gates (e.g., NAND, AND, NOR, OR, XOR, NOT,XNOR, etc.), resistors, multiplexers, registers, capacitors, inductors,diodes, wiring, and so on). The “circuit” may also include one or moreprocessors communicatively coupled to one or more memory or memorydevices. In this regard, the one or more processors may executeinstructions stored in the memory or may execute instructions otherwiseaccessible to the one or more processors. In some embodiments, the oneor more processors may be embodied in various ways. The one or moreprocessors may be constructed in a manner sufficient to perform at leastthe operations described herein. In some embodiments, the one or moreprocessors may be shared by multiple circuits (e.g., circuit A andcircuit B may comprise or otherwise share the same processor which, insome example embodiments, may execute instructions stored, or otherwiseaccessed, via different areas of memory). Alternatively or additionally,the one or more processors may be structured to perform or otherwiseexecute certain operations independent of one or more co-processors. Inother example embodiments, two or more processors may be coupled via abus to enable independent, parallel, pipelined, or multi-threadedinstruction execution. Each processor may be implemented as one or moregeneral-purpose processors, application specific integrated circuits(ASICs), field programmable gate arrays (FPGAs), digital signalprocessors (DSPs), or other suitable electronic data processingcomponents structured to execute instructions provided by memory. Theone or more processors may take the form of a single core processor,multi-core processor (e.g., a dual core processor, triple coreprocessor, quad core processor, etc.), microprocessor, etc. In someembodiments, the one or more processors may be external to theapparatus, for example the one or more processors may be a remoteprocessor (e.g., a cloud based processor). Alternatively oradditionally, the one or more processors may be internal and/or local tothe apparatus. In this regard, a given circuit or components thereof maybe disposed locally (e.g., as part of a local server, a local computingsystem, etc.) or remotely (e.g., as part of a remote server such as acloud based server). To that end, a “circuit” as described herein mayinclude components that are distributed across one or more locations.

Thus, in certain embodiments, the circuits of the engagement systemclient application 140 may be hardware components included with orseparate from the user device 110. In this embodiment, these circuitsmay be structured as described above.

Any foregoing references to currency or funds are intended to includefiat currencies, non-fiat currencies (e.g., precious metals), andmath-based currencies (often referred to as cryptocurrencies). Examplesof math-based currencies include Bitcoin, Litecoin, Dogecoin, and thelike.

It should be noted that although the diagrams herein may show a specificorder and composition of method steps, it is understood that the orderof these steps may differ from what is depicted. For example, two ormore steps may be performed concurrently or with partial concurrence.Also, some method steps that are performed as discrete steps may becombined, steps being performed as a combined step may be separated intodiscrete steps, the sequence of certain processes may be reversed orotherwise varied, and the nature or number of discrete processes may bealtered or varied. The order or sequence of any element or apparatus maybe varied or substituted according to alternative embodiments.Accordingly, all such modifications are intended to be included withinthe scope of the present disclosure as defined in the appended claims.Such variations will depend on the machine-readable media and hardwaresystems chosen and on designer choice. It is understood that all suchvariations are within the scope of the disclosure. Likewise, softwareand web implementations of the present disclosure could be accomplishedwith standard programming techniques with rule based logic and otherlogic to accomplish the various database searching steps, correlationsteps, comparison steps and decision steps.

The foregoing description of embodiments has been presented for purposesof illustration and description. It is not intended to be exhaustive orto limit the disclosure to the precise form disclosed, and modificationsand variations are possible in light of the above teachings or may beacquired from this disclosure. The embodiments were chosen and describedin order to explain the principals of the disclosure and its practicalapplication to enable one skilled in the art to utilize the variousembodiments and with various modifications as are suited to theparticular use contemplated. Other substitutions, modifications, changesand omissions may be made in the design, operating conditions andarrangement of the embodiments without departing from the scope of thepresent disclosure as expressed in the appended claims.

For the purpose of this disclosure, the terms “coupled” or “couple”means the joining of two members directly or indirectly to one another.In this regard, component A may be referred to as being “coupled” tocomponent B even if component C is an intermediary, and component Aexchanges information with component B (e.g., data, commands, values,signals, etc.) via component C. Thus and in this example, there may ormay not be a direct physical connection (e.g., an electrical connection)between component A and component B; yet, for the purposes of thisdisclosure, these components are still considered “coupled.”

What is claimed is:
 1. A computer implemented method of providing athird party engagement in a host property application, the methodcomprising: receiving an indication of an authentication of a user fromthe host property application such that additional authenticationinformation for a third party that provides a third party engagementspecific to the user is not required; via a location positioning systemof a user device associated with the user of the host propertyapplication, determining that the user device is at or near a locationof the third party; receiving an indication of an active user sessionassociated with the host property application while the user device isat or near the location of the third party; generating a third partyengagement specific to the user and associated with the third partybased on the user device being at or near the location of the thirdparty during the same active user session; and providing, via agraphical user interface presented by a display device, the third partyengagement specific to the user during the same active user session. 2.The method of claim 1, further comprising: receiving partnershipinformation regarding one or more products offered by one or moreparticipating third parties.
 3. The method of claim 2, furthercomprising: matching the user to a loyalty program offered by the thirdparty of the one or more participating third parties by identifying thethird party and the loyalty program from the partnership informationbased on transaction data associated with the user of the host propertyapplication.
 4. The method of claim 3, wherein the third partyengagement specific to the user is determined based on the determinationthat the user device is at or near the location of the third party, theassociation of the user with the third party, and the matching of theuser to the loyalty program offered by the third party.
 5. The method ofclaim 1, wherein the third party engagement is at least one of a loyaltycard or a digital stored value card.
 6. The method of claim 1, whereinthe third party engagement is provided in real-time or near real-time.7. The method of claim 1, further comprising: determining a trigger isactivated during the active user session, the trigger comprising anindication that the user device is engaged with the third party.
 8. Asystem for providing a third party engagement in a host propertyapplication, the system comprising: a provider computing systemcommunicatively coupled to a user device, the provider computing systemstructured to: receive an indication of an authentication of a user fromthe host property application such that additional authenticationinformation for a third party that provides the third party engagementspecific to the user is not required; via a location positioning systemof the user device associated with the user of the host propertyapplication, determine that the user device is at or near a location ofthe third party; receive an indication of an active user sessionassociated with the host property application while the user device isat or near the location of the third party; generate a third partyengagement specific to the user and associated with the third partybased on the user device being at or near the location of the thirdparty during the same active user session; and provide, via a graphicaluser interface, the third party engagement specific to the user duringthe same active user session.
 9. The system of claim 8, wherein theprovider computing system is further structured to receive partnershipinformation regarding one or more products offered by one or moreparticipating third parties.
 10. The system of claim 9, wherein theprovider computing system is further structured to match the user to aloyalty program offered by the third party of the one or moreparticipating third parties by identifying the third party and theloyalty program from the partnership information based on transactiondata associated with the user of the host property application.
 11. Thesystem of claim 10, wherein the third party engagement specific to theuser is determined based on the determination that the user device is ator near the location of the third party, the association of the userwith the third party, and the matching of the user to the loyaltyprogram offered by the third party.
 12. The system of claim 8, whereinthe third party engagement is at least one of a loyalty card or adigital stored value card.
 13. The system of claim 8, wherein the thirdparty engagement is provided in real-time or near real-time.
 14. Thesystem of claim 8, wherein the provider computing system is furtherstructured to determine a trigger is activated during the active usersession, the trigger comprising an indication that the user device isengaged with the third party via a transaction at a point of sale deviceassociated with the third party.
 15. A user device, comprising: adisplay device; a processing circuit having at least one processorcoupled to at least one memory storing instructions that, when executedby the at least one processor, cause the processing circuit to:authenticate a user via a host property application such that additionalauthentication information for a third party that provides a third partyengagement specific to the user is not required; via a locationpositioning system, determine that the user device is at or near alocation of the third party; provide an indication of an active usersession associated with the host property application while the userdevice is at or near the location of the third party; receive a thirdparty engagement specific to the user and associated with the thirdparty based on a the user device being at or near the location of thethird party during the same active user session; and provide, via agraphical user interface presented by the display device, the thirdparty engagement specific to the user during the same active usersession.
 16. The user device of claim 15, wherein the instructionsfurther cause the processing circuit to receive partnership informationregarding one or more products offered by one or more participatingthird parties.
 17. The user device of claim 16, wherein the instructionsfurther cause the processing circuit to match the user to a loyaltyprogram offered by the third party of the one or more participatingthird parties by identifying the third party and the loyalty programfrom the partnership information based on transaction data associatedwith the user of the host property application.
 18. The user device ofclaim 17, wherein the third party engagement specific to the user isdetermined based on the determination that the user device is at or nearthe location of the third party, the association of the user with thethird party, and the matching of the user to the loyalty program offeredby the third party.
 19. The user device of claim 15, wherein the thirdparty engagement is at least one of a loyalty card or a digital storedvalue card.
 20. The user device of claim 15, wherein the third partyengagement is provided in real-time or near real-time.